Compiles JSDoc annotated javascript into a Typescript Declaration File (.d.ts).
This library's goal is to be able to take as input a JSDoc annotated source JavaScript file (or many files) and output a single TypeScript Declaration File (.d.ts).
It is distributed as a JSDoc3 template. Running JSDoc with this as the template should result in a TypeScript Definition File.
You can install this module from npm:
$> npm install tsd-jsdoc
To use this module, simply specify it as the template for your normal JSDoc generation.
For example, from the command-line you can do:
$> jsdoc -t node_modules/tsd-jsdoc/dist -r .
Or add this to your JSON configuration:
{
"opts": {
"template": "./node_modules/tsd-jsdoc/dist"
}
}
If you want to use jsdoc/closure tag @template, you also need to specify this module as a plugin, like so:
{
"plugins": [ "./node_modules/tsd-jsdoc/dist/plugin" ],
"opts": {
"template": "./node_modules/tsd-jsdoc/dist"
}
}
This library provides very little validation beyond what JSDoc provides. Meaning if you have invalid JSDoc comments, this will likely output an invalid TypeScript Definition File.
Additionally there are things that JSDoc allows, that TypeScript does not. This library tries to make these differences transparent, and translate from one to the other when necessary. It can't handle anything though, and you can generate invalid Typescript even if your JSDoc is valid.
JSDoc has a bug that prevents it from
correctly parsing export default class Name {}. The workaround is to use named exports
(export class Name {}) or utilize the
jsdoc-export-default-interop plugin.
Tags that describe the code, but support is not implemented are:
@default - No TS equivalent@deprecated - No TS equivalent (issue)@event - No TS equivalent@exports - Everything is exported@external - Not sure what behavior would be expected@fires - No TS equivalent@listens - No TS equivalent@override - No TS equivalent (issue)@throws - No TS equivalentTags that are just metadata and don't actually describe the code are ignored. These are:
@author@classdesc@copyright@description@example@file@license@requires@see@since@summary@todo@tutorial@versionAll other JSDoc tags should work fine.
ClosureCompiler has a couple tags beyond the built-in JSDoc tags that can improve your TypeScript output. Here is a complete list of the tags from CC that are supported in this template:
@template - For genericsJSDoc doesn't have a way to express all the features of typescript so we treat some syntax as special case to create better Typescript.
Class<T> - If we encounter a type that is Class<T> we will treat it as typeof T. See jsdoc3/jsdoc#1349FAQs
Compiles JSDoc annotated javascript into a Typescript Declaration File (.d.ts).
We found that tsd-jsdoc demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.